Software Quality Control is the set of procedures used by organizations[1] to ensure that a software product will meet its quality goals at the best value to the customer,[2] and to continually improve the organization’s ability to produce software products in the future.[1]
Software quality control refers to specified functional requirements as well as non-functional requirements such as supportability, performance and usability.[2] It also refers to the ability for software to perform well in unforeseeable scenarios and to keep a relatively low defect rate.
These specified procedures and outlined requirements leads to the idea of Verification and Validation and software testing.
It is distinct from software quality assurance which includes audits of the quality management system against a standard. Whereas software quality control is a control of products, software quality assurance is a control of processes.
Software Quality Control is the function that checks whether the software project follows its standards processes, and procedures, and that the project produces the desired internal and external (deliverable) products i.e. output.
Quality Control Plan implies to analyze the actions required to fulfill the project requirements such that the end product meets its specifications and product quality is maintained .
The characteristics of the Quality Plan are as follows:
To achieve 5 C's it is recognized that communication between stakeholders and developer is very necessary .
The purpose of Quality Control Plan is to assure that the quality of the product being developed is maintained throughout the development process.The Plan also includes the procedures which assist in controlling the quality of the product.
The main objective of Quality Control Plan is to provide mechanism by which all the plans are executed consistently without any design errors. It ensures that the procedures are continuously reviewed by the stakeholders and the designers. To achieve quality control, a project file document is created where feedback is given at regular intervals. Periodic review of the feedback results in appropriate changes in the development process.
The basic requirements of Quality Control is to fulfill all the valid requirements of the project . It also requires planning , documentation of the project development activities , constant supervision of designer throughout the development process . It also require the developer to ensure that all the project activities are co-ordinated and completed as per schedule and reviews are made periodically.
A Project Quality Control Plan is necessary for each project before starting the project work.
Project Quality Control Plan: This plan gives the detailed information of methods & process that provides the good quality control for all work products.This plan is kept updated with the requirements of project. The plan includes the following parts:
Mainly the QC team contains following members:
Engineer of Record is a professional engineer who controls and supervises all the engineering work performed during project development. The Engineer of Record (EOR)is responsible for developing the Project Quality Control Plan & maintaining the Quality of Project. When the project work starts ,EOR has to make a team for Review & Quality control with the help of Design Engineer. Then the team completes the process to satisfy all the requirements of project & reports it to the designer.
Every Project will undergo this review step. The reviewer is an experienced person who is not an active member of project development team. The different reviews are given below.
These reviews are initialized by Project Management Team . These reviews can take place as part of the Final Plans Processing.
These reviews allow input from these departments ,for constructibility reviews and assist in the Right of Way Office in reducing right of way costs.
In review and checking process, if results are not up to mark, then the checker discuss the issue with design Engineer & tries to solve the issue, If even though the issue is not resolved between the checker and the Designer,then he goes to a senior technical advisor in order to assist in the resolution of the dispute.
The consultants projects should undergo the same Quality Control Plan.
Verification and Validation assures that a software system meets a user's needs.
Verification: "Are we building the product right". The software should conform to its specification.
Validation: "Are we building the right product". The software should do what the user really requires.
Two principal objectives are